Method for broadcasting/multicasting transmissions in wireless networks

ABSTRACT

In a wireless communications network comprising a plurality of multicast and broadcast service (MBS) zones each of which comprises at least one base station, there is provided a method for providing a multicast and broadcast service to a mobile terminal capable of moving from one MBS zone to another. The method comprises the steps of: providing the mobile terminal with one or more multicasting/broadcasting transmissions comprising at least one multicast connection identification (MCID) associated with an MBS zone other than a current MBS zone at which the mobile terminal is currently receiving the one or more multicasting/broadcasting transmissions; retrieving information regarding the at least one MCID; and upon detecting that the mobile terminal is capable of receiving transmissions associated with the other MBS_ZONE, utilizing the MCID associated with that other MBS_ZONE to receive multicasting/broadcasting transmissions intended for that mobile terminal.

CROSS-REFERENCE

This application is a continuation of U.S. patent application Ser. No. 12/921,084, filed on Sep. 3, 2010; which is a '371 National Stage Entry of International Patent Application No. PCT/IL2009/000238, filed on Mar. 2, 2009, which claims benefit of Israeli Patent Application No. 189891, filed on Mar. 3, 2008, the contents of which are incorporated herein by reference in their entireties.

FIELD OF THE INVENTION

The present invention relates to method and apparatus adapted to improve transmission efficiency in wireless communications systems, and more particularly in wireless communications networks that support multicast/broadcast services.

BACKGROUND OF THE INVENTION

Multicast/Broadcast Service (“MBS”) in WiMAX Networks is a service that allows the distribution of data to a group of Mobile Subscribers (“MSs”). IEEE 802.16e standard introduces the notion of MBS_ZONE—aggregation of multiple Base Stations (“BSs”) wherein an MBS SF (“Service Flow”) having a certain SFID (Service Flow Identification) is mapped onto the same Connection Identifier (“CID”) (although in some applications this is done only when there is an identical communication to transmit). In other words, the term “MBS_ZONE” does not typically relate to an area as the same Base Station may belong to more than one MBS_ZONE. Instead, it relates to the flapping of MBS SFIDs onto certain CIDs to enable synchronous broadcast of the same data over the same subchannels at the same time. This technique greatly improves the mobile terminals ability to receive data correctly due to increased energy of the combined signal that each mobile terminal received simultaneously from multiple Base Stations.

MBS Service-now (“SF”) carries information to a set of MSs. Typically there are two methods to access a group of MSs for the provisioning of MBS:

Single-BS: Transmission of data over a single Base Station (“BS”) in the network. The SF is mapped to a Connection Identifier (“CID”) within a specific BS, i.e., the CID is uniquely specified on a “per BS basis”.

Multi-BS: Transmission of data over a plurality of BSs in the network in a synchronized manner. The SF is mapped to a CID unique within a zone at which the service is provided, referred to hereinafter as an “MBS_ZONE”.

The establishment of an MBS connection is typically carded out in a way similar to the way by which unicast connections are established, while the MS registers to the network.

Upon completion of the network entry (“NWE”), the MS is provided with the relevant Multicasting Connection Identifiers (“MCIDs”) and/or with the relevant Logical Channels Identifiers (“LCID”), enabling it to receive the MBS, and this service, is maintained regardless of the current mode of the MS (Normal/Sleep/Idle), so that MBS data is transmitted and received regardless of the MS current operation mode.

The Multi-BS access method enables an MS to receive the MBS content, after having successfully registered and the connection established, from several BSs. As explained above, this transmission method requires that the group of BSs participating in the same Multi-BS-MBS service to be synchronized so that data shall be transmitted by all these BSs simultaneously, and to use the same CID and Security Association (“SA”). It should be noted that the MS does not have to be registered at the specific BS from which it receives MBS transmissions.

As was mentioned hereinbefore, an MBS_ZONE identifier is used to indicate the group of BSs which use the same CID and SA to distribute an MBS SF. MBS_ZONE can be advertised by the BS in DCD messages, also it can be delivered upon establishment of MBS connection and it can be extracted from the MAP_MBS_IE.

Logical Channels are used to distinguish between logical MBS connection for each MBS content delivered within the multicast connection. When used, every MBS content ID is assigned with a Logical Channel Identification (LCID). When an MBS context (within an MCID) is delivered the respective LCID is indicated. Typically, the use of LCIDs and content IDs is vendor specific and depends on the application-layer utilization. When an MS moves from one MBS_ZONE to another and when LCIDs are used, LCID should be re-assigned together with the MCID.

Obviously an MBS_ZONE may include one or more BSs, and a BS may have multiple MBS_ZONE identifiers.

However, one of the drawbacks of the currently known systems is the impact upon the service received by an MS moving from one MBS_ZONE to another, as when the MS detects that it moved to as new MBS_ZONE, it is required to update the MBS Connections IDs (“MCID”s) to match those of the new MBS_ZONE. This updating procedure takes time and while being carried out, it disturbs the reception of all multicast data. Upon entering the new MBS_ZONE, the MCIDs update may be performed either through Location Update (“LU”) procedure (e.g. if the MS is currently in Idle-Mode), by initiating Handover (“HO”) procedure, or by carrying out a complete network entry.

SUMMARY OF THE INVENTION

It is an object of the present invention to provide a method and apparatus that allow efficient and smooth handover (“HO”) process for an MS being a subscriber to MBS.

It is yet another object of the present invention to provide a method and device that enable the MS to retain continuity in the MBS even in cases where the MS that moves from one zone to another is in an idle and/or sleep mode.

It is another object of the present invention to enable efficient MBS by pre-updating multicast connections prior to the transition of the respective MSs to different MBS zones.

Other objects of the invention will become apparent as the description of the invention proceeds.

Thus, in accordance with a first embodiment of the present invention there is provided in a wireless communications network comprising a plurality of MBS zones each comprising at least one Base Station, a method for providing MBS to a mobile terminal capable of moving from one MBS_ZONE to another, the method comprising the steps of:

(i) providing the mobile terminal with one or more multicasting/broadcasting transmissions that comprise at least one MCID associated with an MBS_ZONE other than the current MBS_ZONE at which the mobile terminal is currently receiving these multicasting/broadcasting transmissions;

(ii) retrieving information regarding the at least one MCID, and preferably storing the relevant information at the mobile terminal. More preferably, the information will be retrieved from the currently serving BS and will be associated with MCID belonging to another MBS_ZONE;

(iii) upon detecting that the mobile terminal is capable of receiving transmissions associated with the other MBS zone, utilizing the MCID associated with that other MBS zone to receive multicasting/broadcasting transmissions intended fur that mobile terminal.

According to a preferred embodiment of the invention, the one or more multicasting/broadcasting transmissions comprise MCID values associated with each of the MBS zones that are located adjacent to the current MBS_zone.

According to yet another preferred embodiment of the invention, the at least one MCID is associated with one multicasting/broadcasting transmission every pre-defined period of time.

In accordance with still another preferred embodiment of the invention, the at least one MCID is comprised within the MBS_MAP message. In the alternative or in addition, the at least one MCID is comprised within the data transmission as an Extended Sub-Header (ESH) of a MAC PDU. Preferably but not necessarily, the at least one MCID is associated with a neighboring MBS_ZONE.

By still another preferred embodiment of the invention, the step of retrieving information regarding the at least one MCID further comprising retrieving an MBS zone ID associated therewith.

In accordance with yet another preferred embodiment of the invention, the method provided further comprises a step wherein the step of utilizing the MCID associated with that other MBS_ZONE is carried out upon identifying by the mobile terminal that it communicates with a different Base Station which is associated with to different MBS_ZONE for which that MCID is associated (valid).

According to another embodiment of the invention, the mobile terminal is provided with MBS data at the new MBS zone concurrently while carrying out a Location Update (“LU”) procedure or Handover (“HO”).

In accordance with still another embodiment of the invention, Only BSs located at the MBS zone boundaries include information regarding the at least one MCID in their multicasting/broadcasting transmission.

By yet another embodiment of the invention, the information regarding the at least one MCID provided by the Base Station is associated with MBS_ZONES adjacent to the transmitting BS. In other words, within a specific MBS_ZONE, different Base Stations may include different information regarding the at least one MCID in their respective multicasting/broadcasting transmissions, where that at least one MCID is associated with an MBS_ZONE to which the BS adjacent to the transmitting BS, belongs.

According to another embodiment of the invention, the information regarding the at least one MCID is divided and transmitted in a plurality of transmissions (or frames). By this embodiment, a single transmission will not have to be loaded with all information regarding the various MCIDs and their respective MBS zones pairs that are the neighboring MBS zones of the current MBS zone.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, reference is made to the following detailed description taken in conjunction with the accompanying drawings wherein:

FIG. 1—illustrates a flow chart of a process of an MS receiving MBS data and MAP, and the extraction of MCID/LCID Update information;

FIG. 2—illustrates an MS Updating Scheme which relates to actions to be taken by the MS when a new BS with new MBS_ZONE ID is detected; and

FIG. 3—demonstrates a time flow describing the movement of an MS from one MBS_ZONE to another.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

A better understanding of the present invention is obtained when considering the following non-limiting detailed examples taken in conjunction with the drawings.

The method provided by the present invention, enables the provisioning a multicast and broadcast service to a mobile terminal capable of moving from one MBS_ZONE to another irrespective of its operation mode when the move takes place, an operation mode which may be at the time of the change in the MBS_ZONE normal (active) mode, idle mode or even sleep mode, although typically but not necessarily when the MS moves to another MBS_ZONE while being in a sleep mode, its sleep mode will be terminated in order to enable that MS to carry out a handover procedure with the new BS.

The method is based on the idea that when the mobile terminal communicates with a base station which transmits MBS data to the mobile terminal, a base station that belongs to the current MBS zone (i.e. before moving to the new zone), it also provides the mobile terminal with multicast connection identifications (MCIDs), defining connections along which that service can be provided for the mobile terminal in other MBS zones. Preferably, in MBS zones located at the vicinity of the base station and/or of the mobile terminal current location.

Let us consider now FIG. 1 where MBS data or MBS MAP is received at the MS (step 100). The received signal is checked to determine if it comprises MBS data or MBS MAP (step 110). if the signal has been determined to comprise MBS MAP, then the MS retrieves the MBS location and offset (step 120). Next, it extracts the location and offset of the next MBS MAP (step 130), and then it extracts the updated TLV of MCIDs/LCIDs (step 140). If the received signal comprises MBS data, then the MS retrieves the relevant MBS stream (step 150) and then extracts the MCIDs/LCIDs updates from the ESH (step 160). Upon extracting the MCIDs/LCIDs updated information, it is stored at the MS (step 170), and the latter awaits the receipt of the next transmission comprising MAP/data to update the MCID/s/LCIDs accordingly (if necessary).

The MCIDs related information is preferably provided to the mobile terminal as part of the multicast/broadcast transmissions it receives from its serving Base Station. Upon receiving these transmissions, the mobile terminal parses the MCID update information and keeps the relevant MCIDs information thereat. The information transmitted includes parameters associated with MBS_ZONEs, and typically includes pairs of ID of other MBS zone(s) with their corresponding new MCIDs.

The serving base station updates this information preferably on a periodic basis (and not every multicast/broadcast transmission), but as will be appreciated by those skilled in the art, any other update scheme should be understood as being encompassed by the present invention, and the MS keeps the most updated information.

By the process illustrated in FIG. 2, when the MS detects that due to its movement, the MBS_ZONE has been changed, i.e., the BS from which it is due to get the service is part of another MBS_ZONE (step 200), it would first validate the ID of the MBS_ZONE (step 210), and if the MBS_ZONE has been changed (step 220), it will retrieve and the MCIDs/LCIDs related to this new MBS_ZONE (step 230) and change (update) the MCIDs according to the information that is kept at the mobile terminal, without undue delays (step 240). The MS will remain with the updated MCIDs as long as no changes are detected in the serving BS (step 250). If such changes are detected, the process starts again at step 200. Therefore the solution provided by the present invention enables the MS to continue receiving MBS data while concurrently updating its location or registering at the new base station, e.g. while performing as location update procedure, by carrying out as handover procedure, or other applicable type of a registration procedure. As was previously explained, connectivity is maintained while following the method of the present invention regardless of the state of the mobile terminal (MS), even during Idle-Mode and Sleep-Mode. Preferably, the same MCID value is provided for several connections established with different MSs that have been registered to receive the same service, e.g., transmissions associated with a certain TV channel.

FIG. 3 a time flow is demonstrated, which relates to the movement of an MS from one MBS_ZONE to another. Once the MS detects that it is about to be serviced by another (new) BS which is associated with a new MBS_ZONE ID, the MS performs:

1. MCIDs/LCIDs updates; and

2. HO/LU procedure.

Preferably, the distribution of MCIDs' updated values associated with neighboring MBS_ZONEs is carried out as part of the multicast/broadcast transmissions. Such updates can be part of the frame map or within the data transmission. In other words, the MCID Update information (TLV) can be part of one of the DL messages, such as MBS_MAP message, and/or an extended sub-headers (ESH) may convey such information as in the TLV, within the MCID PDU.

In each of the following Tables 1, 2 and 3 there is provided a non-limiting example of possible TLVs for conveying MCID updating information via the MBS_MAP message. By the example of Table 1, the current MCID and the new MCID are shown within a certain MBS zone. In the example of Table 2 the current MCID and a 9 bits delta value (i.e. the difference between the current MCID value and a new MCID value within the MCIDs range, required to calculate the new MCID within a certain MBS zone). The example of Table 3 shows the service flow identification (“SFID”) and the new multicast connection identification (MCID) within a given MBS zone.

TABLE 1 MCID Update TLV with current and new MCID information. Type Length Value Scope XXX N × (16 + 16 + 8) = N × N × (Current_MCID, MBS_MAP 40 bits New_MCID, MBS_ZONE_ID)

TABLE 2 MCID Update TLV with current MCID and delta information. Type Length Value Scope XXX N × (16 + 9 + 8 + 3) = N × N × (Current_MCID, MBS_MAP 36 bits Delta, MBS_ZONE_ID)

TABLE 3 MCID Update TLV with SFID and new MCID information. Type Length Value Scope XXX N × (32 + 16 + 8) = N × 56 N × (SFID, MBS_MAP Bits New_MCID, MBS_ZONE_ID)

Each of the following Tables 4, 5 and 6 illustrates to non-limiting example of conveying MCID updating information via an MBS PDU using an ESH. The example of Table 4 includes the current MCID and the new MCID within a certain MBS zone. Table 5 illustrates the provisioning of the current MCID and the delta value required to calculate the new MCID within a certain MBS zone, while by the example of Table 6, the SFID and the new MCID within a certain MBS zone, are provided.

TABLE 4 MCID Update ESH with current and new MCID information. Name Size (bits) Description Current MCID 16 MCID used in the current MBS zone New MCID 16 MCID to be used in the MBS zone indicated in the MBS zone ID field MBS zone ID 8 A new MBS zone

TABLE 5 MCID Update ESH with MCID and Delta information. Name Size (bits) Description Current MCID 16 MCID used in current MBS zone Delta 9 The difference for calculating new MCID from current MCID, for the MBS zone indicated by the MBS zone ID field MBS zone ID 8 A new MBS zone Reserved 3

TABLE 6 MCID Update ESH with SFID and new MCID information. Name Size (bits) Description New MCID 16 MCID to be used in the MBS zone indicated by the MBS zone ID field SFID 32 The service flow ID MBS zone ID 8 A new MBS zone

MCIDs used for MBS are preferably taken from the range of 0xFEA0-0xFEFE (94 connections). Therefore, MCIDs can also be represented by using 12 bits string. This allows further reduction in the size of TLVs and ESHs exemplified above.

The table below illustrates an LCID update TLV. The assignment of LCID to MBS Content ID is similar to the method provided by the IEEE-802.16e standard during Multicast connection establishment (through DSA transaction) where a 1 byte long LCID is paired with the 2 byte long MBS Content ID.

TABLE 7 LCID update TLV Type Length Value Scope XXX 8 + 16 + N × 16) = 24 + N × (MBS_ZONE_ID, MBS_MAP N × 16 bits New_MCID, MBS Content ID(0), MBS Content ID(1), . . . MBS Content ID(N − 1))

TABLE 8 a possible way of combining both MCID update and LCID update. Type Length Value Scope XXX N × (16 + 16 + 8 + 8 + N × (Current_MCID, MBS_MAP M × 16) = N × (48 + New_MCID, M × 16) bits MBS_ZONE_ID, Number of MBS Contents IDs, MBS Content ID(0), MBS Content ID(1), . . . MBS Content ID(N − 1))

TABLE 9 a possible update of a single MCID and its LCIDs Type Length Value Scope XXX 16 + 16 + 8 + N × 16 = 40 + Current_MCID, MBS_MAP N × 16 bits New_MCID, MBS_ZONE_ID, N × (MBS Content ID(0), MBS Content ID(1), . . . MBS Content ID(N − 1))

As will be appreciated by those skilled in the art, the above description includes only some embodiments of the method for providing smooth transition of mobile terminals between one MBS zone to another without interfering with the multicast service, and serves for its illustration. It should be understood that a number of other ways of carrying out the method provided by the present invention may be devised by a person skilled in the art without departing horn the scope of the invention, and are thus encompassed by the present invention.

The present invention has been described using non-limiting preferred embodiments thereof that are provided by way of example and are not intended to limit the scope of the invention. Variations of embodiments described will occur to persons of the art. Furthermore, the terms “comprise”, “include”, “have” and their conjugates, shall mean, when used in the claims, “including but not necessarily limited to.” 

We claim:
 1. A method for providing a multicast and broadcast service (MBS) in a wireless communications network where one or more base stations transmit synchronously, comprising: enabling a base station of the one or more base stations to simultaneously support MBS services and unicast services; associating a first MBS service flow with a first logical channel identifier for a first MBS zone and a second MBS service flow with a second logical channel identifier for a second MBS zone; establishing an MBS connection between the base station and a mobile terminal presently located in a first MBS zone; receiving and storing at the mobile terminal the first and second logical channel identifiers; receiving at the mobile terminal the base station the first MBS service flow associated with the first logical channel identifier; and when the mobile device detects a zone change from the first MBS zone to the second MBS zone, receiving at the mobile terminal the first MBS service flow associated with the second logical channel identifier, while retaining continuity of the MBS service.
 2. A method as claimed in claim 1, wherein the mobile station receives the second MBS zone identifier from the base station.
 3. A method as claimed in claim 1, wherein a zone hand-over is performed during the mobile station operation in an idle mode.
 4. A method for providing a multicast and broadcast service (MBS) in as wireless communications network by a base station transmitting synchronously with other base stations, comprising: transmitting at least one unicast service flow; establishing an MBS connection to as mobile terminal in to first MBS zone; associating an MBS service flow with a logical channel identifier for the first MBS zone; transmitting to the mobile terminal the MBS service flow associated with the logical channel identifier; and transmitting to the mobile terminal a second logical channel identifier associated with a second MBS service flow for a second MBS zone; wherein the second logical channel identifier is for use by the mobile terminal in a hand-over from the first MBS zone to the second MBS zone, during the mobile station operation in an idle mode, using the second logical channel identifier, while retaining continuity of the MBS service.
 5. A method for maintaining continuity of service of a multicast and broadcast service (MBS) in a wireless communications network where one or more base stations transmit synchronously, comprising: establishing at least one unicast connection with a first base station; receiving from the first base station a first logical channel identifier associated with a first MBS service flow in a first MBS zone; receiving from a first base station a second logical channel identifier associated with a second MBS service flow in a second MBS zone; and performing, during the mobile station operation in an idle mode, a hand-over from the first base station to a second base station of the one or more base stations using the second logical channel identifier, while retaining the continuity of the MBS service. 